TagLibTest.WriteID3v2Tag test fails under windows

Bug #1628780 reported by Sébastien BLAISOT
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Undecided
Sébastien BLAISOT

Bug Description

[----------] 1 test from TagLibTest
[ RUN ] TagLibTest.WriteID3v2Tag
src\test\taglibtest.cpp(37): error: Value of: QFile::remove(tmpFileName)
  Actual: false
Expected: true
[ FAILED ] TagLibTest.WriteID3v2Tag (1 ms)
[----------] 1 test from TagLibTest (1 ms total)

Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :

Which version of Qt did you use?

The failed assertion simply checks that the temporary file has actually been removed before reusing its generated file name for copying an existing file over it. You can safely remove this assertion and run the test again.

Changed in mixxx:
assignee: nobody → Uwe Klotz (uklotzde)
Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :

Btw, I'm looking for updated instructions on how to easily set up a Windows build environment ;) The instructions in the Wiki never worked out of the box and I don't have time to figure this out.

Revision history for this message
Sébastien BLAISOT (sblaisot) wrote :

I'm using QT 4.8.7

If you Want, I can put somewhere my prebuilt Windows build env. This way , you only have to download and extract it plus install the build tools (msvs, python, nsis,...)

Revision history for this message
Sébastien BLAISOT (sblaisot) wrote :

I suspect open() creates a file under linux, but only creates the file under windows when effectively writing into it.

I don't understand why exists() returns true, even if you move it after close().

Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :

If you are able to upload your working Windows build environment somewhere that would be great :) I need only the compiled 3rd-party components and maybe some hints about the required directory structure.

Are we still using VS2013?

Revision history for this message
Sébastien BLAISOT (sblaisot) wrote :

yes, I'm using VS2013, this was the recommended compiler at the time I built my mixxx-2.0 build env ;)
I wait for Pegasus to finish his work on the mixxx-2.1 build env to switch to VS2015, QT5 and updated build env.

I'll upload my prebuilt windows build env for you this afternoon.

Revision history for this message
Sébastien BLAISOT (sblaisot) wrote :

Why don't you directly use your QTemporaryFile object in your test and create a second QFile copiedFile object ?
As far as I understand, QTemporaryFile inherits all methods of QFile.

Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :

As far as I can remember this workaround was necessary to obtain a generated, unique file name for a temporary file. Maybe we can find a better way to achieve this.

Revision history for this message
Sébastien BLAISOT (sblaisot) wrote :
Changed in mixxx:
assignee: Uwe Klotz (uklotzde) → Sébastien BLAISOT (sblaisot)
Revision history for this message
Sébastien BLAISOT (sblaisot) wrote :
Changed in mixxx:
status: New → Fix Committed
Changed in mixxx:
milestone: none → 2.1.0
Changed in mixxx:
status: Fix Committed → Fix Released
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/8657

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.