Conversation
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
4 similar comments
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
|
@Kelvinrr This should be ready for a review. I guess there is still the question of whether or not these changes are API breaking. |
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
1 similar comment
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
3e0c293 to
aa1c64e
Compare
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
|
Rebased and no new tests failing outside of the dev test failures. |
aa1c64e to
aefbe64
Compare
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
1 similar comment
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
7b81765 to
15d3a81
Compare
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
2 similar comments
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
* Fixed pvl core test config * Changed cmake_source to project_source for submodule
…ase-folding file system
…the build and install
cbd926e to
e7ba576
Compare
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
acpaquette
left a comment
There was a problem hiding this comment.
A couple small things to fix
| @@ -0,0 +1,29 @@ | |||
| #include "Constants.h" | |||
There was a problem hiding this comment.
Did this file not get moved from isis/tests/ConstantsTest.cpp
isis/Makefile
Outdated
| #ISISLIBVERSION := $(shell echo $(ISISMAJOR).$(ISISMINOR).$(ISISMINORMINOR) | sed 's/[a-z].*$$//') | ||
| #ISISLOCALVERSION := $(shell head -n 3 $(ISISROOT)/version | tail -n 1 | sed 's/\#.*//' | sed 's/ *$$//') | ||
| #ISISRELEASE := REL_0_0 | ||
| # CMAKE generated file: DO NOT EDIT! |
There was a problem hiding this comment.
It's weird that this didn't cause an issue. Can we try reverting this file and see if the tests pass?
There was a problem hiding this comment.
A bunch of tests are now failing after I reverted this Makefile
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5717". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
Description
Related Issue
How Has This Been Validated?
Types of changes
Checklist:
Licensing
This project is mostly composed of free and unencumbered software released into the public domain, and we are unlikely to accept contributions that are not also released into the public domain. Somewhere near the top of each file should have these words: