Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refresh MusicBrainz JSON responses used for testing #365

Merged
merged 3 commits into from
Feb 13, 2019

Conversation

Freso
Copy link
Member

@Freso Freso commented Feb 13, 2019

Some of these dumps predate when MusicBrainz had (re)introduced track MBIDs, so some tests for the code for #200 would fail since the JSON dumps didn't contain those IDs.

Original commit followed up by two commits that fix test cases that were now failing, due to the data having been fixed in MusicBrainz.

Some of these dumps predate when MusicBrainz had (re)introduced track
MBIDs, so some tests for the code for issue #200 would fail since the
JSON dumps didn't contain those IDs.

Signed-off-by: Frederik “Freso” S. Olesen <freso.dk@gmail.com>
@Freso Freso force-pushed the task/refresh-musicbrainz-json-responses branch from d39fe3a to 37e3ecb Compare February 13, 2019 16:40
The previous release has gotten a release date added since it was
originally dumped from MusicBrainz.

Signed-off-by: Frederik “Freso” S. Olesen <freso.dk@gmail.com>
The previously used release has since had its [unknown] artist credit
resolved since the data was originally taken from MusicBrainz.

Using data from this release now:
https://musicbrainz.org/release/8478d4da-0cda-4e46-ae8c-1eeacfa5cf37
Specifically:
https://musicbrainz.org/track/a04ee451-46c3-3ad6-a815-d7bb8449d605

Signed-off-by: Frederik “Freso” S. Olesen <freso.dk@gmail.com>
@Freso Freso force-pushed the task/refresh-musicbrainz-json-responses branch from 37e3ecb to fce00f4 Compare February 13, 2019 17:36
@JoeLametta JoeLametta merged commit 1cf784c into develop Feb 13, 2019
@JoeLametta JoeLametta deleted the task/refresh-musicbrainz-json-responses branch February 13, 2019 17:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants