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

bump version to 0.1.3 to permit release on CI #72

Merged
merged 16 commits into from
Dec 12, 2020
Merged

Conversation

dcchivian
Copy link

No description provided.

@@ -1,3 +1,9 @@
#0.1.3
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like @jsfillman, @Tianhao-Gu and @qzzhang added code without release notes for 1.2 and 1.3 - can the 3 of you update the release notes please?

We should probably add a checklist or something, as I merged a PR without release notes myself. Should've caught that.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 updated release note for 0.1.2.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @Tianhao-Gu . I increased the version to v0.1.3 because there was a new commit with respect to the v0.1.2 that's released on CI (and it blocks re-release of the same version). That implies there was another change after the first v0.1.2. Anyone know what that change was? Maybe I can figure it out from the commit logs, but I figure you all might know rather than me resort to code forensics.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually, it wasn't too bad. The released commit on CI is df0bb65 which was from @qzzhang. Ever commit after than is from @jsfillman and appears to be his cleanup of our github framework. Not sure what that release note should be. @jsfillman what should we say is the change in RELEASE_NOTES.md for v0.1.3?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@qzzhang do you mind adding some release notes for #67 ?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MrCreosote @Tianhao-Gu @jsfillman @qzzhang where are we at with this? are the only changes still to record in the release notes the github stuff from @jsfillman and the colon to underscore for SHOCK names?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MrCreosote I went ahead and added what I could for the comments. I'd really like to merge this so I can register it on CI.KBASE.US and do integration testing of client modules against it. I'm sure @jsfillman would be better able to describe what changes he made between v0.1.2 and v0.1.3 (which I'm considering everything after commit df0bb65), but I made a much more general comment so we can get this through. What do you think?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated the release note for #67, then it created a new branch and pr #73.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also added release notes as requested in #74.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

merged your RELEASE_NOTES changes. Working on errors in unit tests now.

@MrCreosote
Copy link
Member

Looks like tests are failing

Copy link
Contributor

@jsfillman jsfillman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's see if we can find what stopped passing after commit d8091ef. 🤷

@dcchivian
Copy link
Author

@jsfillman sounds good. Looks like the old log expired, but I suspect the current errors in the SDK unit tests are the same as the old commit. There appear to be 5 unit tests that are failing. https://github.com/kbaseapps/DataFileUtil/pull/72/checks?check_run_id=1477112011

@dcchivian
Copy link
Author

4 errors/failures related to ftp tests (maybe the data on that path has been removed?) and one that appears to be a noclobber with a repeat path from another test

@dcchivian
Copy link
Author

some of the tests are failing trying to do an ftp from ftp.uconn.edu. that address does not ping. not sure why that server was picked, but maybe we can test against a server from NCBI? Need to dig more to see whether the type of data matters...

@dcchivian
Copy link
Author

some of the tests are failing trying to do an ftp from ftp.uconn.edu. that address does not ping. not sure why that server was picked, but maybe we can test against a server from NCBI? Need to dig more to see whether the type of data matters...

looks some of the tests actually want to save the test file that is subsequently downloaded. not sure what server we can use for that. thoughts?

@codecov
Copy link

codecov bot commented Dec 2, 2020

Codecov Report

Merging #72 (dd6a938) into master (e36bf01) will decrease coverage by 0.08%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #72      +/-   ##
==========================================
- Coverage   70.30%   70.21%   -0.09%     
==========================================
  Files           3        3              
  Lines        1155     1155              
==========================================
- Hits          812      811       -1     
- Misses        343      344       +1     
Impacted Files Coverage Δ
lib/DataFileUtil/DataFileUtilImpl.py 91.23% <0.00%> (-0.15%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e36bf01...dd6a938. Read the comment docs.

Copy link
Contributor

@jsfillman jsfillman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some of the tests are failing trying to do an ftp from ftp.uconn.edu. that address does not ping. not sure why that server was picked, but maybe we can test against a server from NCBI? Need to dig more to see whether the type of data matters...

looks some of the tests actually want to save the test file that is subsequently downloaded. not sure what server we can use for that. thoughts?

@Tianhao-Gu's fix seemed to do the trick!

@dcchivian
Copy link
Author

dcchivian commented Dec 3, 2020

unit tests are passing. travis-ci is failing on "make sdkbase". is the travis base image not using a pre-built kbase image? @MrCreosote @jsfillman @Tianhao-Gu @qzzhang how should we proceed? My feeling is the travis-ci is an issue that should be fixed, but seems beyond the scope of this PR for DataFileUtil. If you agree, then @MrCreosote should probably merge. Gavin, do you agree?

(also, the RELEASE_NOTES.md has been updated, which Gavin identified as needing to happen)

@MrCreosote
Copy link
Member

I think we wanted to merge this PR to get the release notes correct before the 0.1.3 bump: #73

@qzzhang There's an open question for you - can you take a look?

IMO we should have the tests passing before we merge. It looks like they did pass at least once since we got code coverage, so it should be doable.

@MrCreosote
Copy link
Member

From https://github.com/kbaseapps/DataFileUtil/commits/master, it looks like the tests broke here: c3a61c9

@dcchivian
Copy link
Author

I think we wanted to merge this PR to get the release notes correct before the 0.1.3 bump: #73

@qzzhang There's an open question for you - can you take a look?

I think @Tianhao-Gu included the RELEASE_NOTES.md that @qzzhang put into #73, so merging #73 would be redundant. However, she should confirm that note on the : to _ filename change belongs with 0.1.1

@dcchivian
Copy link
Author

From https://github.com/kbaseapps/DataFileUtil/commits/master, it looks like the tests broke here: c3a61c9

looking at the tests from that commit, it's not travis-ci that was broken back then rather the SDK unit tests that are passing now. however, we still need to fix the current travis-ci issue with "make sdkbase". I have no idea why it's building from scratch. is it always supposed to do that? @jsfillman @MrCreosote do you happen to know?

@MrCreosote
Copy link
Member

@jsfillman Do we even need travis anymore or is it all covered by GHA?

qzzhang and others added 2 commits December 8, 2020 19:40
- blobstore fails earlier with a more relevant error message when presented
   with an invalid uuid
- blobstore will not accept node data without a file

Note that while making these changes, 4 google drive tests started
failing for unknown reasons. It seems extremly unlikely that the
changes here caused that.
@dcchivian
Copy link
Author

dcchivian commented Dec 11, 2020

@MrCreosote @jsfillman @Tianhao-Gu @qzzhang so the remaining error is in travis-ci and seems to be connected to blobstore. Is that a blocker to merging? Guessing yes since Gavin appears to be actively working on it, but please confirm.

@MrCreosote
Copy link
Member

The last build that completed showed the make sdkbase error: https://travis-ci.org/github/kbaseapps/DataFileUtil/builds/748460971

Switching to Github Actions. GHA does everything the travis.yml file
does, but also runs tests.
@MrCreosote
Copy link
Member

couple of follow on issues for this PR:
#80
#79

@MrCreosote MrCreosote merged commit 99129b3 into master Dec 12, 2020
@MrCreosote MrCreosote deleted the dcchivian-patch-1 branch December 12, 2020 00:22
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.

5 participants