householder: mismatch between GIT HEAD and the continuous built for the 6.0 branch

classic Classic list List threaded Threaded
3 messages Options
Samuel GOUGEON Samuel GOUGEON
Reply | Threaded
Open this post in threaded view
|

householder: mismatch between GIT HEAD and the continuous built for the 6.0 branch

Hello devs,

I wanted to fix an issue with the householder() demo: in the Jenkins built, the file
SCI/modules/linear_algebra/macros/householder.sce
is missing while householder.sci exec() it when entering householder()
without input argument. So, this situation yields an error when entering householder().

But when browsing the GIT after a
$ git reset --hard origin/6.0
as usual, one sees that
SCI/modules/linear_algebra/macros/householder.sce
actually exists and is the right file!

I have checked that it is not a matter of OS file hidding.

So, how is this possible??
Is there a way to check the built processing, in order to understand where a file is finally removed (or may be other ones added or changed)?

Regards
Samuel



_______________________________________________
dev mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/dev
Antoine ELIAS-2 Antoine ELIAS-2
Reply | Threaded
Open this post in threaded view
|

Re: householder: mismatch between GIT HEAD and the continuous built for the 6.0 branch

Hello Samuel,

I think the issue comes from linear_algebra.iss, it does not install *.sce files from macros folder.
I will patch 6.0 branch to add this file or .sce in Windows installer.

Regards,
Antoine
Le 09/12/2017 à 22:29, Samuel Gougeon a écrit :

Hello devs,

I wanted to fix an issue with the householder() demo: in the Jenkins built, the file
SCI/modules/linear_algebra/macros/householder.sce
is missing while householder.sci exec() it when entering householder()
without input argument. So, this situation yields an error when entering householder().

But when browsing the GIT after a
$ git reset --hard origin/6.0
as usual, one sees that
SCI/modules/linear_algebra/macros/householder.sce
actually exists and is the right file!

I have checked that it is not a matter of OS file hidding.

So, how is this possible??
Is there a way to check the built processing, in order to understand where a file is finally removed (or may be other ones added or changed)?

Regards
Samuel




_______________________________________________
dev mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/dev


_______________________________________________
dev mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/dev
Samuel GOUGEON Samuel GOUGEON
Reply | Threaded
Open this post in threaded view
|

Re: householder: mismatch between GIT HEAD and the continuous built for the 6.0 branch

Hello Antoine,

Thanks for this clear explanation. It sets some light about the role of *.iss files,
that -- so -- do some pre(or post?)compiling actions.
Actually, checking after reading your message,  linear_algebra.iss does not copy all *.sce files
in the macros directory.

The linear_algebra module has a unusual ./examples subdirectory. I think this is the best
place where to move the householder.sce example file. linear_algebra.iss copies all *sce from/to it.
I am going to patch the 6.0 branch in this way, and will set you as reviewer.

Thanks
Best regards
Samuel

Le 10/12/2017 à 03:20, Antoine ELIAS a écrit :
Hello Samuel,

I think the issue comes from linear_algebra.iss, it does not install *.sce files from macros folder.
I will patch 6.0 branch to add this file or .sce in Windows installer.

Regards,
Antoine
Le 09/12/2017 à 22:29, Samuel Gougeon a écrit :

Hello devs,

I wanted to fix an issue with the householder() demo: in the Jenkins built, the file
SCI/modules/linear_algebra/macros/householder.sce
is missing while householder.sci exec() it when entering householder()
without input argument. So, this situation yields an error when entering householder().

But when browsing the GIT after a
$ git reset --hard origin/6.0
as usual, one sees that
SCI/modules/linear_algebra/macros/householder.sce
actually exists and is the right file!

I have checked that it is not a matter of OS file hidding.

So, how is this possible??
Is there a way to check the built processing, in order to understand where a file is finally removed (or may be other ones added or changed)?

Regards
Samuel




_______________________________________________
dev mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/dev



_______________________________________________
dev mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/dev



_______________________________________________
dev mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/dev